Method and apparatus for supporting migration and co-existence of public land mobile network based on user equipment capability identifications

ABSTRACT

A method, apparatus and computer program product are provided for intelligently switching from public land mobile network (PLMN) assigned identification (ID) to UE manufacturer assigned ID. An example method includes receiving a registration request message comprising information related to location registration to an access and mobility management function (AMF) or a mobility management entity (MME) through a radio access network (RAN), obtaining an international mobile equipment identity (IMEI) or Permanent Equipment Identifier (PEI) of a user equipment and extracting from the IMEI or PEI a type allocation code (TAC). The method then obtains a user equipment radio capability ID associated with the user equipment and determines whether the UE shall use a user equipment manufacturer ID or PLMN assigned ID in order to determine an appropriate registration accept message having instructions to operate based on the user equipment manufacturer ID or the PLMN assigned ID.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Application No.62/842,109 filed May 2, 2019, which is hereby incorporated herein in itsentirety by reference.

BACKGROUND

Third generation partnership project (3GPP) 5^(th) generation (5G)technology is a next generation of radio systems and networkarchitecture that can deliver extreme broadband and ultra-robust, lowlatency connectivity. 5G technology improves a variety oftelecommunication services offered to the end users, and helps tosupport massive broadband that delivers gigabytes of bandwidth persecond on demand for both the uplink and downlink transmissions. Nextgeneration systems, which utilize the 5G architecture, utilizevirtualized radio access network (RAN) functions and core networkfunctions.

In general, in a mobile system, a User Equipment (UE) provides thenetwork with RAN and network UE capabilities. The size of the UE radiocapabilities information such information can over time becomesignificant. One concept used in 5G mobile networks, which is beingdefined in 3GPP Release 16 under the feature Optimizations of UE radiocapability signaling (RACS) and is to be documented, for example but notlimited to, in 3GPP technical specification (TS) 23.501, TS 23.501 andTS 23.401, is the concept of providing a centralized node such as a UEcapabilities Management Function (UCMF) to allocate and store a UEcapability identification (ID) that represents the radio capabilities ofthe UE, or to store a dictionary, provided by a UE manufacturer, the UEcapability ID(s) representing the UE radio capabilities of the UE modelidentified by a type allocation code (TAC). The Type Allocation Code(TAC) is issued by the GSM Association in its capacity as the GlobalDecimal Administrator. Further information can be found in the GSMATS.06 “IMEI Allocation and Approval Process”. This UE capability ID, ifallocated by the PLMN using the UCMF, is provided to the UE and storedin the UE and is also known as PLMN-assigned UE Radio Capability ID (seeTS 23.501). The IDs that are stored in the UCMF and UE as defined by theUE manufacturers and associated to the UE model TAC are also known as UEmanufacturer-assigned UE radio Capability ID (see TS 23.501). Themapping of the ID to the related capabilities is also cached in the corenetwork (CN) and RAN nodes. This UE capability ID is then sent by the UEto the network in registration messages in the 5G system (5GS, see TS23.501) or attach messages and/or in in tracking area update messages inevolved packet system (EPS, see TS 23.401) so the network is aware ofthe UE ratio capabilities without then inquiring the full set ofcapabilities thus minimizing signalling size over the radio network. TheUE may be identified/associated in the network in a 5GS using aPermanent Equipment Identity (PEI) and in the EPS by using anInternational Mobile Equipment Identity (IMEI). The PEI and IMEI formatis the same and includes the TAC of the UE model. See TS 23.003.

However, there is a problem associated with switching from a public landmobile network (PLMN) assigned ID to a UE manufacturer assigned ID.Solutions are now being investigated in 3GPP, for example, solution 1proposes using a “flush” indication in an appropriate Non-Access-Stratum(NAS) procedure indicating to the UE that it should delete any PLMNassigned UE Capability IDs that it has for the PLMN. Accordingly, nexttime the UE performs the registration procedure, the UE either indicatesits manufacturer assigned ID (assuming it has one) or it does notinclude any ID, which will trigger the network to re-acquire the UEradio access capability over the air.

One issue with this proposal is that UEs which are not configured with amanufacturer assigned ID will unnecessarily need to signal their radioaccess capability over the air again. Also for such UEs (with nomanufacturer assigned ID) the network needs to take care to not ask thesame UE more than once (e.g. by using a new ID value range for the newlyassigned PLMN assigned IDs). Additionally, the “flush” indication issent indiscriminately to all UEs, which leads to unnecessary UE radioaccess capability re-acquisition over the radio for UEs that do not havea manufacturer assigned IDs.

Another proposed solution 2 is built on top of solution 1, with theaddition of an indicator that the UE provides to the network along withthe PLMN assigned UE capability ID, indicating that the UE “also has aconfigured manufacturer assigned ID.” Based on this additional indicatorthe network knows that it should send a “flush” indication only to UEsthat have a configured manufacturer based ID. One issue with solution 2is that the “flush” indication is sent only to UEs that do not have amanufacturer assigned ID for a specific set of UE radio accesscapabilities causing added logic complexity on the network side.

A third solution which is similar to solution 1 with the only differencebeing that the “flush” message is interpreted conditionally by the UEe.g. “delete a PLMN-assigned ID for this PLMN under the condition thatyou have a manufacturer assigned ID for the same set of UE radio accesscapabilities.” At least one issue with solution 3 is that the “flush”indication is sent to all UEs, however, the re-acquisition of UE radioaccess capability over the radio is performed only for UEs that do nothave a manufacturer-assigned ID.

BRIEF SUMMARY

A method, apparatus, and computer program product are provided inaccordance with certain example embodiments in order to intelligentlyswitch from a public land mobile network (PLMN) assigned identification(ID) to a UE manufacturer assigned ID. In this regard, an embodiment ofthe present disclosure proposes an approach that does not require arudimentary indicator but instead provides intelligence about what UEssupport the UE manufacturer capability ID in the network.

In one example embodiment, a method is provided that includes receiving,from a user equipment, a registration request message comprisinginformation related to location registration to an access and mobilitymanagement function (AMF) or a mobility management entity (MME) througha radio access network (RAN), obtaining an international mobileequipment identity (IMEI) or permanent equipment identifier (PEI) of theuser equipment and extracting a type allocation code (TAC) from the IMEIor the PEI and obtaining a user equipment radio capabilityidentification (ID) associated with the user equipment. The registrationrequest message indicates that the user equipment supports userequipment radio capability signaling (RACS). The user equipment radiocapability ID represents the user equipment's radio access capabilitiesinformation. The method further includes determining whether the userequipment radio capability ID is a user equipment manufacturer ID or apublic land mobile network (PLMN) assigned ID and comparing the userequipment's TAC with a list of TACs enabled to operate according to arespective user equipment manufacturer ID. In circumstances where theuser equipment's TAC appears on the list and the user equipment's userequipment radio capability ID is the public land mobile network (PLMN)assigned ID, the method further includes constructing a registrationaccept message, wherein the registration accept message includesinstructions for the user equipment to: 1) operate based on the userequipment manufacturer ID, 2) delete PLMN assigned IDs the userequipment stores for respective PLMNs and 3) trigger the user equipmentto register with the user equipment manufacturer ID associated with acurrent user equipment radio configuration. In circumstances where theuser equipment's TAC does not appear on the list and the userequipment's user equipment radio capability ID is the user equipmentmanufacturer ID, the method further includes constructing theregistration accept message, wherein the registration accept messageincludes instructions for the user equipment to operate based on thePLMN assigned ID. The method then includes transmitting the registrationaccept message to the user equipment.

In some implementations the method further includes assigning the PLMNassigned ID and constructing the registration accept message, whereinthe registration accept message includes instructions for the userequipment to operate based on the PLMN assigned ID in circumstanceswhere the user equipment's TAC does not appear on the list and the userequipment's user equipment radio capability ID is not determined. Incircumstances where the user equipment's TAC appears on the list and theuser equipment's user equipment radio capability ID is not determined,the method includes constructing the registration accept message,wherein the registration accept message includes instructions for theuser equipment to operate based on the user equipment manufacturer ID.

In some implementations the method further includes storing the assignedPLMN assigned ID as the user equipment radio capability ID along withtheir associated TACs and transmitting a notification of a switch fromthe PLMN assigned ID to the user equipment manufacturer ID andvice-versa for a specific TAC. Thereafter, when an indication isreceived to switch to the user equipment manufacturer ID for thespecific TAC, the method further includes removing the association ofthe PLMN assigned ID to the specific TAC. In another exampleimplementation, the method includes removing the dissociated PLMNassigned ID from storage when the PLMN assigned ID becomes disassociatedto the specific TAC. The method then includes transmitting a messageinstruction to a user equipment capabilities management function (UCMF)to store the assigned PLMN assigned ID and associate the assigned PLMNassigned ID to the specific TAC.

In some embodiments, the method further includes determining whether tocommence assignment of the user equipment manufacturer ID or the PLMNassigned ID by obtaining the TAC from the IMEI or the PEI, identifying amanufacturer identifier of the user equipment based on the TAC, andverifying the manufacturer identifier with a predetermined list ofstored manufacturer identifiers.

In another example embodiment, an apparatus is provided that includesmeans for receiving, from a user equipment, a registration requestmessage comprising information related to location registration to anaccess and mobility management function (AMF) or a mobility managemententity (MME) through a radio access network (RAN), means for obtainingan international mobile equipment identity (IMEI) or permanent equipmentidentifier (PEI) of the user equipment and extracting a type allocationcode (TAC) from the IMEI or the PEI and means for obtaining a userequipment radio capability identification (ID) associated with the userequipment. The user equipment radio capability ID represents the userequipment's radio access capabilities information. The apparatus furtherincludes means for determining whether the user equipment radiocapability ID is a user equipment manufacturer ID or a public landmobile network (PLMN) assigned ID and means for comparing the userequipment's TAC with a list of TACs enabled to operate according to arespective user equipment manufacturer ID. In circumstances where theuser equipment's TAC appears on the list and the user equipment's userequipment radio capability ID is the public land mobile network (PLMN)assigned ID, the apparatus further includes means for constructing aregistration accept message, wherein the registration accept messageincludes instructions for the user equipment to: 1) operate based on theuser equipment manufacturer ID, 2) delete PLMN assigned IDs the userequipment stores for respective PLMNs and 3) trigger the user equipmentto register with the user equipment manufacturer ID associated with acurrent user equipment radio configuration. In circumstances where theuser equipment's TAC does not appear on the list and the userequipment's user equipment radio capability ID is the user equipmentmanufacturer ID, the apparatus further includes means for constructingthe registration accept message, wherein the registration accept messageincludes instructions for the user equipment to operate based on thePLMN assigned ID. The apparatus further includes means for transmittingthe registration accept message to the user equipment.

In another example embodiment, an apparatus is provided that includes atleast one processor and at least one memory including computer programcode for one or more programs with the at least one memory and thecomputer program code configured to, with the at least one processor,cause the apparatus at least to receive, from a user equipment, aregistration request message comprising information related to locationregistration to an access and mobility management function (AMF) or amobility management entity (MME) through a radio access network (RAN),obtain an international mobile equipment identity (IMEI) or permanentequipment identifier (PEI) of the user equipment and extracting a typeallocation code (TAC) from the IMEI or the PEI and obtain a userequipment radio capability identification (ID) associated with the userequipment. The user equipment radio capability ID represents the userequipment's radio access capabilities information. The computer programcode is further configured to, with the at least one processor, causethe apparatus to determine whether the user equipment radio capabilityID is a user equipment manufacturer ID or a public land mobile network(PLMN) assigned ID and compare the user equipment's TAC with a list ofTACs enabled to operate according to a respective user equipmentmanufacturer ID. In circumstances where the user equipment's TAC appearson the list and the user equipment's user equipment radio capability IDis the public land mobile network (PLMN) assigned ID, the computerprogram code is further configured to, with the at least one processor,cause the apparatus to construct a registration accept message, whereinthe registration accept message includes instructions for the userequipment to: 1) operate based on the user equipment manufacturer ID, 2)delete PLMN assigned IDs the user equipment stores for respective PLMNsand 3) trigger the user equipment to register with the user equipmentmanufacturer ID associated with a current user equipment radioconfiguration. In circumstances where the user equipment's TAC does notappear on the list and the user equipment's user equipment radiocapability ID is the user equipment manufacturer ID, the computerprogram code is further configured to, with the at least one processor,cause the apparatus to construct the registration accept message,wherein the registration accept message includes instructions for theuser equipment to operate based on the PLMN assigned ID. The computerprogram code is further configured to, with the at least one processor,cause the apparatus to transmit the registration accept message to theuser equipment.

In another example embodiment, a computer program product is providedthat includes at least one non-transitory computer-readable storagemedium having computer executable program code instructions storedtherein with the computer executable program code instructionscomprising program code instructions configured, upon execution, toreceive, from a user equipment, a registration request messagecomprising information related to location registration to an access andmobility management function (AMF) or a mobility management entity (MME)through a radio access network (RAN), obtain an international mobileequipment identity (IMEI) or permanent equipment identifier (PEI) of theuser equipment and extracting a type allocation code (TAC) from the IMEIor the PEI and obtain a user equipment radio capability identification(ID) associated with the user equipment. The user equipment radiocapability ID represents the user equipment's radio access capabilitiesinformation. The computer executable program code instructionscomprising program code instructions is further configured, uponexecution, to determine whether the user equipment radio capability IDis a user equipment manufacturer ID or a public land mobile network(PLMN) assigned ID and compare the user equipment's TAC with a list ofTACs enabled to operate according to a respective user equipmentmanufacturer ID. In circumstances where the user equipment's TAC appearson the list and the user equipment's user equipment radio capability IDis the public land mobile network (PLMN) assigned ID, the computerexecutable program code instructions comprising program codeinstructions is further configured, upon execution, to construct aregistration accept message, wherein the registration accept messageincludes instructions for the user equipment to: 1) operate based on theuser equipment manufacturer ID, 2) delete PLMN assigned IDs the userequipment stores for respective PLMNs and 3) trigger the user equipmentto register with the user equipment manufacturer ID associated with acurrent user equipment radio configuration. In circumstances where theuser equipment's TAC does not appear on the list and the userequipment's user equipment radio capability ID is the user equipmentmanufacturer ID, the computer executable program code instructionscomprising program code instructions is further configured, uponexecution, to construct the registration accept message, wherein theregistration accept message includes instructions for the user equipmentto operate based on the PLMN assigned ID. The computer executableprogram code instructions comprising program code instructions isfurther configured, upon execution, to transmit the registration acceptmessage to the user equipment.

In yet another example embodiment, a method is provided that includestransmitting a location registration request message to an access andmobility management function (AMF) or a mobility management entity (MME)through a radio access network (RAN) and identifying a current userequipment radio configuration associated with the registration request.The method further includes receiving a registration accept messagecomprising a user equipment radio capability identification (ID). Incircumstances where the registration accept message indicatesinstructions to operate according to a user equipment manufacturer ID,the method further provides for deleting stored public land mobilenetwork (PLMN) assigned IDs and re-registering using the user equipmentmanufacturer ID associated with the current user equipment radioconfiguration as the user equipment radio capability ID. Incircumstances where the registration accept message indicatesinstructions to operate according to a PLMN assigned ID, the methodfurther includes associating the PLMN assigned ID to the current userequipment radio configuration.

In another example embodiment, an apparatus is provide comprising meansfor transmitting a location registration request message to an accessand mobility management function (AMF) or a mobility management entity(MME) through a radio access network (RAN) and means for identifying acurrent user equipment radio configuration associated with theregistration request. The apparatus further provides for means forreceiving a registration accept message comprising a user equipmentradio capability identification (ID). In circumstances where theregistration accept message indicates instructions to operate accordingto a user equipment manufacturer ID, the apparatus further providesmeans for deleting stored public land mobile network (PLMN) assigned IDsand re-registering using the user equipment manufacturer ID associatedwith the current user equipment radio configuration as the userequipment radio capability ID. In circumstances where the registrationaccept message indicates instructions to operate according to a PLMNassigned ID, the apparatus includes means for associating the PLMNassigned ID to the current user equipment radio configuration.

In another example embodiment, an apparatus is provided that includes atleast one processor and at least one memory including computer programcode for one or more programs with the at least one memory and thecomputer program code configured to, with the at least one processor,cause the apparatus at least to transmit a location registration requestmessage to an access and mobility management function (AMF) or amobility management entity (MME) through a radio access network (RAN),identify a current user equipment radio configuration associated withthe registration request, and receive a registration accept messagecomprising a user equipment radio capability identification (ID). Incircumstances where the registration accept message indicatesinstructions to operate according to a user equipment manufacturer ID,the at least one memory and the computer program code is furtherconfigured to, with the at least one processor, cause the apparatus atleast to delete stored public land mobile network (PLMN) assigned IDsand re-registering using the user equipment manufacturer ID associatedwith the current user equipment radio configuration as the userequipment radio capability ID. In circumstances where the registrationaccept message indicates instructions to operate according to a PLMNassigned ID, the at least one memory and the computer program code isfurther configured to, with the at least one processor, cause theapparatus at least to associate the PLMN assigned ID to the current userequipment radio configuration.

In yet another example embodiment, a computer program product isprovided that includes at least one non-transitory computer-readablestorage medium having computer executable program code instructionsstored therein with the computer executable program code instructionscomprising program code instructions configured, upon execution, totransmit a location registration request message to an access andmobility management function (AMF) or a mobility management entity (MME)through a radio access network (RAN), identify a current user equipmentradio configuration associated with the registration request, andreceive a registration accept message comprising a user equipment radiocapability identification (ID). The computer executable program codeinstructions comprising program code instructions is further configured,upon execution, to delete stored public land mobile network (PLMN)assigned IDs and re-registering using the user equipment manufacturer IDassociated with the current user equipment radio configuration as theuser equipment radio capability ID in circumstances where theregistration accept message indicates instructions to operate accordingto a user equipment manufacturer ID. In circumstances where theregistration accept message indicates instructions to operate accordingto a PLMN assigned ID, the computer executable program code instructionscomprising program code instructions is further configured, uponexecution, to associate the PLMN assigned ID to the current userequipment radio configuration.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described certain example embodiments of the invention ingeneral terms, reference will now be made to the accompanying drawings,which are not necessarily drawn to scale, and wherein:

FIG. 1 illustrates a system architecture in accordance with an exampleembodiment of the present disclosure;

FIG. 2 illustrates a system architecture in accordance with an exampleembodiment of the present disclosure;

FIG. 3 is a block diagram of a core network apparatus configured inaccordance with an example embodiment of the present disclosure;

FIG. 4 illustrates example transmissions between a user equipment and aradio capabilities signalling optimization (RACS) network in accordancewith an example embodiment of the present disclosure;

FIGS. 5A and 5B illustrate an international mobile station equipmentidentity and software version number in accordance with an exampleembodiment of the present disclosure;

FIGS. 6A and 6B are flowcharts illustrating methods for intelligentlyswitching from a public land mobile network (PLMN) assignedidentification (ID) to an UE manufacturer assigned ID as describedherein;

FIG. 7 is a block diagram of a user equipment configured in accordancewith an example embodiment of the present disclosure; and

FIG. 8 is a flowchart illustrating methods for intelligently switchingoperations from a public land mobile network (PLMN) assignedidentification (ID) to an UE manufacturer assigned ID as describedherein.

DETAILED DESCRIPTION

Some embodiments of the present invention will now be described morefully hereinafter with reference to the accompanying drawings, in whichsome, but not all, embodiments of the invention are shown. Indeed,various embodiments of the invention may be embodied in many differentforms and should not be construed as limited to the embodiments setforth herein; rather, these embodiments are provided so that thisdisclosure will satisfy applicable legal requirements. Like referencenumerals refer to like elements throughout. As used herein, the terms“data,” “content,” “information,” and similar terms may be usedinterchangeably to refer to data capable of being transmitted, receivedand/or stored in accordance with embodiments of the present invention.Thus, use of any such terms should not be taken to limit the spirit andscope of embodiments of the present invention.

Additionally, as used herein, the term ‘circuitry’ refers to (a)hardware-only circuit implementations (e.g., implementations in analogcircuitry and/or digital circuitry); (b) combinations of circuits andcomputer program product(s) comprising software and/or firmwareinstructions stored on one or more computer readable memories that worktogether to cause an apparatus to perform one or more functionsdescribed herein; and (c) circuits, such as, for example, amicroprocessor(s) or a portion of a microprocessor(s), that requiresoftware or firmware for operation even if the software or firmware isnot physically present. This definition of ‘circuitry’ applies to alluses of this term herein, including in any claims. As a further example,as used herein, the term ‘circuitry’ also includes an implementationcomprising one or more processors and/or portion(s) thereof andaccompanying software and/or firmware. As defined herein, a“computer-readable storage medium,” which refers to a physical storagemedium (e.g., volatile or non-volatile memory device), may bedifferentiated from a “computer-readable transmission medium,” whichrefers to an electromagnetic signal.

A method, apparatus and computer program product are provided inaccordance with an example embodiment to provide efficient approach forsignalling UE radio access capability information over the radiointerface and other network interfaces as described herein.

FIG. 1 depicts a 5G system architecture having radio capabilitiessignalling optimization (RACS) in accordance with an example embodimentof the present disclosure. In general, under RACS, the network willsupport an efficient approach to signal UE radio access capabilityinformation over the radio interface and other network interfaces. RACSworks by assigning an identifier to represent a set of UE radiocapabilities. This identifier is called UE radio capabilityidentification (ID). A UE radio capability ID can be either UEmanufacturer assigned or PLMN assigned. The UE radio capability ID is analternative to the signalling of the radio capabilities container overthe radio interface, within NG-RAN, from NG-RAN to E-UTRAN, from AMF toNG-RAN and between CN nodes supporting RACS.

As shown in FIG. 1 and in FIG. 2, the 5G system architecture may consistof the following network functions (NF): Authentication Server Function(AUSF), Access and Mobility Management Function (AMF), Data Network(DN), e.g. operator services, Internet access or 3rd party services,Unstructured Data Storage Function (UDSF), Network Exposure Function(NEF), Network Repository Function (NRF), Network Slice SelectionFunction (NSSF), Policy Control Function (PCF), Session ManagementFunction (SMF), Unified Data Management (UDM), Unified Data Repository(UDR), User Plane Function (UPF), UE radio Capability ManagementFunction (UCMF), Application Function (AF), User Equipment (UE), NextGeneration-Radio Access Network (NG-RAN), 5G-Equipment Identity Register(5G-EIR), Network Data Analytics Function (NWDAF), and Charging Function(CHF). The 5G system architecture may further comprise the followingnetwork entities: Service Communication Proxy (SCP) and Security EdgeProtection Proxy (SEPP).

FIG. 2 depicts the UE MME Core Network Capability that is split into the51 UE MME network capability (mostly for E-UTRAN access related corenetwork parameters) and the Core Network Capability (mostly to includeother UE capabilities related to 5GCN or interworking with EPS) andcontains non radio-related capabilities, e.g. the NAS securityalgorithms (not shown) etc. The 51 UE MME network capability istransferred between all CN nodes at AMF to AMF, AMF to MME, MME to MME,and MME to AMF changes. The 5GMM capability is transferred only at AMFto AMF changes.

In order to ensure that the UE identity stored in the USIM (UniversalSubscriber Identity Module) is authenticated and registered with theSystem, the UE RM and network capabilities and the UE locationinformation stored in the AMF is up to date the UE s perform initialRegistration and mobility registration update procedure within the NASmessage. The UE may include the UE radio capability ID in such messages.

Additionally or alternatively, if the UE's UE RM Core Network Capabilityinformation changes (in either CM-CONNECTED or in CM-IDLE state), the UEshall perform a Mobility Registration Update procedure when it nextreturns to NG-RAN coverage. The UE may include the UE radio capabilityID in this message.

FIGS. 1 and 2 further include the following service-based interfaces:Namf: Service-based interface exhibited by AMF; Nsmf: Service-basedinterface exhibited by SMF; Nnef: Service-based interface exhibited byNEF; Npcf: Service-based interface exhibited by PCF; Nudm: Service-basedinterface exhibited by UDM; Naf: Service-based interface exhibited byAF; Nnrf: Service-based interface exhibited by NRF; Nnssf: Service-basedinterface exhibited by NSSF; Nausf: Service-based interface exhibited byAUSF; Nudr: Service-based interface exhibited by UDR; Nudsf:Service-based interface exhibited by UDSF; N5g-eir: Service-basedinterface exhibited by 5G-EIR; Nnwdaf: Service-based interface exhibitedby NWDAF; Nchf: Service-based interface exhibited by CHF; and Nucmf:Service-based interface exhibited by UCMF.

Moreover, although the foregoing descriptions and the associateddrawings describe certain example embodiments in the context of animproved 5G communication system, it should be appreciated that othercommunication systems may be provided by alternative embodiments withoutdeparting from the scope of the appended claims. Although 5G technologyand 5G systems are employed herein, they are used in a illustrative anddescriptive sense only and not for purposes of limitation.

As described above, the UE radio capability information containsinformation on radio capabilities that the UE supports (e.g. powerclass, frequency bands, etc). Consequently, this information can besufficiently large that it is undesirable to send it across the radiointerface at every transition of UE connection management (CM) state inthe AMF from CM-IDLE to CM-CONNECTED. In an example embodiment, in orderto avoid this radio overhead, the AMF shall store the UE Capabilityinformation during the CM-IDLE state for the UE and RM-REGISTERED statefor the UE and the AMF shall, when available, send its most up to dateUE Radio Capability information to the RAN in the N2 REQUEST messagesent on the N2 interface as shown in FIG. 1. The AMF then deletes the UEradio capability when the UE RM state in the AMF transitions toRM-DEREGISTERED. In an example embodiment, the UE Radio Capability ismaintained in the core network, even during AMF reselection.

In an example embodiment, the number of PLMN assigned IDs that the UEstores in non-volatile memory is left up to UE implementation. However,to minimise the load from radio signalling on the UE interface and toprovide smoother inter-PLMN mobility (e.g. at land borders) the UE shallbe able to store at least the latest 16 PLMN-assigned IDs, for example,(along with the PLMN that is assigned to them). In some embodiments,this number is independent of the UE Radio Capability ID(s) the UE maystore.

Additionally or alternatively, the UE may be configured to change, e.g.upon change in its usage settings, the set of UE Radio Capabilities intime and signal the associated UE Radio Capability ID, if available. TheUE may then be configured to store the mapping between the UE RadioCapability ID and the corresponding UE Radio Capability information forevery UE Radio Capability ID. Accordingly, the NG-RAN may apply RRCfiltering of UE radio capabilities when it retrieves the UE RadioCapabilities information from the UE.

In circumstances when the UE's NG-RAN UE radio capability informationchanges while in CM-IDLE state, the UE shall perform the registrationprocedure with the registration type set to mobility registration updateindicating “UE Radio Capability Update”. When the AMF receives mobilityregistration update request with “UE Radio Capability Update”, it shalldelete any UE radio capability information that it has stored for theUE.

In an example embodiment when the trigger to change the UE's NG-RAN UEradio capability information happens when the UE is in CM-CONNECTEDstate, the UE shall first enter CM-IDLE state and then perform theregistration procedure with the registration type set to mobilityregistration update indicating “UE Radio Capability Update”. The RANstores the UE radio capability information, received in the N2 messageor obtained from the UE, for the duration of the UE staying in radioresource control (RRC)s connected or RRC Inactive state.

The UCMF (UE radio Capability Management Function) stores all UE RadioCapability ID mappings in a PLMN and is responsible for assigning everyPLMN-assigned UE Radio Capability ID in this PLMN.

In an example embodiment, in order to be able to interpret the UE RadioCapability ID a Network Function or node may store a local copy of themapping between the UE Radio Capability ID and its corresponding UERadio Access Capabilities information e.g. a dictionary entry. When nomapping is available between a UE Radio Capability ID and thecorresponding UE Radio Capability information in a Network Function ornode, this Network Function or node shall be able to retrieve it andstore it.

In an example embodiment, in an instance when the NG-RAN needs toretrieve the mapping of a UE Radio Capability ID to the corresponding UERadio Capability information, it queries the AMF using N2 signalling.For example, the AMF retrieves the UE Radio Capability Information itprovides it to UCMF in order to obtain a mapping of a UE RadioCapability ID to the corresponding UE Radio Capabilities information.

In an example embodiment, a UE that supports RACS stores an applicableUE Radio Capability ID for the current UE Radio Configuration in thePLMN, it shall signal the UE Radio Capability ID in the InitialRegistration procedure. If both PLMN-assigned for the current PLMN andUE manufacturer-assigned UE Radio Capability IDs are stored in the UEand applicable in the PLMN, the UE shall signal the PLMN assigned UERadio Capability ID in the Registration Request message.

In some examples when a PLMN decides to switch to operate based onmanufacturer-assigned UE Radio Capability ID for a particular TACidentifying a UE model, the UCMF indicates to the AMFs it is in contactwith that the specific TAC operates in UE manufacturer-assigned UE RadioCapability ID mode such that the AMF indicates to the NG-RAN nodes it isin contact with via a N2 message that the specific TAC operates in UEmanufacturer-assigned UE Radio Capability ID mode.

In some networks, the AMF indicates to UEs that register with thespecific TAC value in the PEI and providing a PLMN-assigned UE RadioCapability ID that the PLMN requires it to operate based on UEmanufacturer-assigned UE Radio Capability IDs. A UE that receives suchindication in the Registration Accept message deletes any PLMN assignedIDs it stores for the PLMN so that this UE shall use the UEmanufacturer-assigned UE Radio Capability IDs until the PLMN provides itwith any PLMN-assigned UE Radio Capability ID. In addition, the UEproceeds to Register with the UE manufacturer assigned UE RadioCapability ID that is applicable to the current UE Radio configurationso that the system is aware of its current UE Radio Capability ID andrelated UE radio capabilities.

In an example embodiment, the UE Radio Capability ID may be a shortpointer that is used to uniquely identify a set of UE RadioCapabilities. The UE Radio Capability ID is assigned either by theserving PLMN or by the UE manufacturer. The manufacturer-assigned UERadio Capability ID may be assigned by the UE manufacturer in which caseit is accompanied with the UE manufacturer information. In this case,the UE Radio Capability ID uniquely identifies a set of UE RadioCapabilities for this manufacturer, and together with this UEmanufacturer information uniquely identify this set of UE RadioCapabilities in any PLMN.

In the PLMN-assigned ID, when a manufacturer-assigned UE RadioCapability ID is not used by the UE or the serving network, or it is notrecognized/stored by the serving PLMN UCMF, the UCMF may allocate UERadio Capability IDs for the UE corresponding to different sets of UERadio capabilities the PLMN may receive from the UE at different times.In this case, the UE Radio Capability IDs the UE receives are applicableto the serving PLMN and uniquely identify the corresponding sets of UERadio Capabilities in this PLMN.

The type of UE Radio Capability ID (Manufacturer-assigned orPLMN-assigned) is distinguished when a UE Radio Capability ID issignalled. The NG-RAN and the AMF caching (or storing in the UEcontexts) the PLMN-assigned UE Radio Capability IDs keeps an associationto the TAC of the UE model that they are related to. When a PLMNswitches to UE manufacturer-assigned UE Radio Capability ID for aparticular UE model TAC, all PLMN-assigned UE Radio Capability IDrelated to this TAC can be removed from the cache with priority,irrespective of the caching policies.

In yet another example embodiment, the AMF keeps a list of TACs that areenabled to use UE manufacturer IDs (or it can query the UCMF to detectwhether there is a database of UE manufacturer assigned IDs for the TACof the UE). This can be progressively populated by the UCMF when theUCMF receives the dictionary for a TAC. If a UE registers with the AMFwith a PLMN assigned type of UE capability ID and the TAC of the UE isin this list, the AMF shall indicate to the UE in Registration acceptmessage that the PLMN requires sending the UE manufacturer assigned UECapability IDs and not the PLMN assigned ID. This will be the behaviourthe UE stores for this PLMN even when the UE is deregistered. To thiseffect, the UE erases all the PLMN assigned IDs for the PLMN when itreceives indication the PLMN supports UE manufacturer assigned. The UEre-registers immediately with a UE manufacturer assigned UE CapabilityID.

In instances when the AMF or the MME receives an indication of theswitch from a PLMN assigned ID to a UE manufacturer assigned ID for aTAC value, the AMF or MME may be configured to check all the contexts ofthe UEs they store and if the IMEI/PEI contains such TAC value, the UEsget updated by the network on whether to use UE manufacturer assignedIDs or PLMN assigned IDs by means of a UE configuration update message(by AMF in 5GS) or a globally unique temporary ID (GUTI) reallocationcommand message (by MME in EPS).

In an example embodiment, an attach procedure can occur when powering-onthe UE or when the UE enters a network. The UE registers via theregistration request message with the network to receive services thatrequire registration. In an attach procedure, the UE transmits an“attach request” or “tracking area update request” to the network andthe network affirms the attach request with an attach accept messagesuch as, for example, an “attach accept” or “tracking area updateaccept.” In various embodiments, the “attach accept” or “tracking areaupdate accept” message can be modified to include instructions whetherthe UE shall use a UE manufacturer assigned ID or PLMN assigned ID.

In an instance when the UE registers with a UE manufacturer assigned UECapability ID but the PLMN does not store the UE manufacturer assignedUE Capability IDs and their mapping to UE Radio capabilities for thisTAC, then the AMF indicates in registration accept to use PLMN assignedID. A PLMN assigned ID is then provided to the UE for the UE currentradio capabilities. This ID could also be directly provided in theregistration accept message (so no indication is needed), or separatelyin a UE configuration update after the UE registration completes. Thisinformation shall be stored and clears any previous information that theUE shall use UE manufacturer assigned UE Capability IDs (implicitlyanyhow a UE that has a PLMN assigned ID shall use it). This enables toswitch from UE manufacturer assigned ID to PLMN assigned ID method or itallows to use PLMN assigned ID in a PLMN where some UEs can operate inPLMN assigned mode even if they have a UE manufacturer ID assigned bythe manufacturer (e.g. the PLMN operator has not yet got the dictionaryfor that UE model) but some UE models for which the UCMF stores thedictionary can use UE-manufacturer assigned mode.

In another example embodiment when the UE registers without indicatingany UE capability ID, but the UE indicates it supports the RACS feature,then the PLMN assigned ID is provided if the UE's TAC is not in the listof UE model that use UE-manufacturer-assigned UE capability ID.Otherwise an indication is provided to use UE manufacturer-assigned UEcapability ID.

The RAN and CN store the PLMN assigned IDs with the related TAC, so theRAN and CN can receive indication these are stale when the UEmanufacturer assigned UE Capability IDs become supported for a UE TAC ina PLMN. The TAC that switches to UE manufacturer assigned UE CapabilityIDs is indicated to the RAN via non-UE associated signalling by the AMF.The UCMF allows AMFs to subscribe to updates of what TAC use UEmanufacturer assigned UE Capability IDs as, e.g., the UCMF is populatedwith the related UE manufacturer assigned UE Capability IDs and the UCMFis therefore ready to resolve these IDs. Likewise if for a certain TAC,for any reason, the stops using the UE manufacturer assigned ID the UCMFmay notify the AMF

In an example embodiment, each PLMN-assigned ID should be associated inthe RAN and CN caches to the TACs it is associated with. The TAC of theUE needs all the time to be transferred and passed in signallinginterfaces between network nodes when the related PLMN-assigned UEcapability ID is sent. When a PLMN assigned UE capability ID that iscached in the RAN or AMF has no association with any TAC because all ofthe IMEIs they relate to have transitioned to UE manufacturer assignedUE capability ID, then it is removed from the cache.

Turning now to FIG. 3, in order to embody the RACS including a UEcapability management function (UCMF), a RAN and an access and mobilitymanagement function (AMF), an apparatus 10 is provided and as shown, forexample, in FIG. 3. The apparatus may be embodied by any of a variety ofdifferent components such as different nodes of a 5G RACS-capablenetwork architecture instance.

As shown in FIG. 3, the apparatus of an example embodiment includes, isassociated with or is otherwise in communication with a processor 12, anassociated memory 14 and a communication interface 16.

The processor 12 (and/or co-processors or any other circuitry assistingor otherwise associated with the processor) may be in communication withthe memory device 14 via a bus for passing information among componentsof the apparatus 10. The memory device may be non-transitory and mayinclude, for example, one or more volatile and/or non-volatile memories.In other words, for example, the memory device may be an electronicstorage device (e.g., a computer readable storage medium) comprisinggates configured to store data (e.g., bits) that may be retrievable by amachine (e.g., a computing device like the processor). The memory devicemay be configured to store information, data, content, applications,instructions, or the like for enabling the apparatus to carry outvarious functions in accordance with an example embodiment of thepresent disclosure. For example, the memory device could be configuredto buffer input data for processing by the processor. Additionally oralternatively, the memory device could be configured to storeinstructions for execution by the processor.

The apparatus 10 may, in some embodiments, be embodied in variouscomputing devices as described above. However, in some embodiments, theapparatus may be embodied as a chip or chip set. In other words, theapparatus may comprise one or more physical packages (e.g., chips)including materials, components and/or wires on a structural assembly(e.g., a baseboard). The structural assembly may provide physicalstrength, conservation of size, and/or limitation of electricalinteraction for component circuitry included thereon. The apparatus maytherefore, in some cases, be configured to implement an embodiment ofthe present disclosure on a single chip or as a single “system on achip.” As such, in some cases, a chip or chipset may constitute meansfor performing one or more operations for providing the functionalitiesdescribed herein.

The processor 12 may be embodied in a number of different ways. Forexample, the processor may be embodied as one or more of varioushardware processing means such as a coprocessor, a microprocessor, acontroller, a digital signal processor (DSP), a processing element withor without an accompanying DSP, or various other circuitry includingintegrated circuits such as, for example, an ASIC (application specificintegrated circuit), an FPGA (field programmable gate array), amicrocontroller unit (MCU), a hardware accelerator, a special-purposecomputer chip, or the like. As such, in some embodiments, the processormay include one or more processing cores configured to performindependently. A multi-core processor may enable multiprocessing withina single physical package. Additionally or alternatively, the processormay include one or more processors configured in tandem via the bus toenable independent execution of instructions, pipelining and/ormultithreading.

In an example embodiment, the processor 12 may be configured to executeinstructions stored in the memory device 14 or otherwise accessible tothe processor. Alternatively or additionally, the processor may beconfigured to execute hard coded functionality. As such, whetherconfigured by hardware or software methods, or by a combination thereof,the processor may represent an entity (e.g., physically embodied incircuitry) capable of performing operations according to an embodimentof the present disclosure while configured accordingly. Thus, forexample, when the processor is embodied as an ASIC, FPGA or the like,the processor may be specifically configured hardware for conducting theoperations described herein. Alternatively, as another example, when theprocessor is embodied as an executor of instructions, the instructionsmay specifically configure the processor to perform the algorithmsand/or operations described herein when the instructions are executed.However, in some cases, the processor may be a processor of a specificdevice (e.g., an image processing system) configured to employ anembodiment of the present disclosure by further configuration of theprocessor by instructions for performing the algorithms and/oroperations described herein. The processor may include, among otherthings, a clock, an arithmetic logic unit (ALU) and logic gatesconfigured to support operation of the processor.

The communication interface 16 may be any means such as a device orcircuitry embodied in either hardware or a combination of hardware andsoftware that is configured to receive and/or transmit data from/to anetwork. In this regard, the communication interface may include, forexample, an antenna (or multiple antennas) and supporting hardwareand/or software for enabling communications with a wirelesscommunication network. Additionally or alternatively, the communicationinterface may include the circuitry for interacting with the antenna(s)to cause transmission of signals via the antenna(s) or to handle receiptof signals received via the antenna(s). In some environments, thecommunication interface may alternatively or also support wiredcommunication. As such, for example, the communication interface mayinclude a communication modem and/or other hardware/software forsupporting communication via cable, digital subscriber line (DSL),universal serial bus (USB) or other mechanisms.

Turning now to FIG. 4 illustrating operations of intelligently switchingfrom public land mobile network (PLMN) assigned identification (ID) toUE manufacturer assigned ID. In an example embodiment, the AMFs mayswitch to UE manufacturer assigned ID based RACS by TAC. Accordingly,when a UCMF is populated with the UE manufacturer assigned UE CapabilityIDs, it shall indicate to the AMFs that a certain TAC now can use UEmanufacturer assigned UE Capability IDs. For example, the UCMF providesthe UE manufacturer assigned UE Capability IDs to the AMF, and thesebear the TAC of the UE model that is affected such that when the UEregisters the Registration Accept message provides the UE with positiveindication the UE can start using the UE manufacturer IDs.

Accordingly, the RACS-capable network provides for a centralized nodesuch as the UCMF to allocate and store the UE capability ID thatrepresents the radio capabilities of the UE, or to store a dictionary,provided by a UE manufacturer, the UE capability ID(s) representing theUE radio capabilities of the UE model identified by the TAC.

As discussed above, the UE capability ID, if allocated by the PLMN usingthe UCMF, is provided to the UE and stored in the UE and is also knownas PLMN-assigned UE Radio Capability ID. The IDs that are stored in theUCMF and UE as defined by the UE manufacturers and associated to the UEmodel TAC are also known as UE manufacturer-assigned UE radio CapabilityID. The mapping of the ID to the related capabilities is also cached inthe core network (CN) and RAN nodes. The UE capability ID is then sentby the UE to the network in registration messages in the 5G system sothe network is aware of the UE ratio capabilities without then inquiringthe full set of capabilities thus minimizing signalling size over theradio network. The UE may be identified/associated in the network in a5GS using the TAC of the UE model.

In an example embodiment, block 40 illustrates that the UCMF isconfigured with the UE manufacturer assigned UE radio capability IDs fora UE model with type allocation code (TAC) indicating a manufactureridentifier. In another embodiment, the AMF keeps a list of TACs that areenabled to use UE manufacturer IDs. The list may be progressivelypopulated by the UCMF when the UCMF receives the dictionary for a TACfrom a UE manufacturer. Such a list shall be kept in non-volatilestorage. In block 42, the UCMF notifies the AMF of a TAC thattransitions to UE manufacturer assigned UE radio capability ID.Accordingly, the AMF stores the list comprising the UE model TACsindicating instructions for operating according to a respective userequipment manufacturer ID.

In block 46, a registration request is received from the UE and in block48 the AMF indicates to the UE to use the UE manufacturer assigned UEradio capability ID and delete the PLMN assigned UE radio capability ID.At this time, the UE shall proceed to a further registration indicatingthe UE manufacturer-assigned UE radio capability ID applicable to thecurrent UE radio configuration (e.g. corresponding to the current radiointerface technologies that are enabled or disabled etc.)

FIG. 5A illustrates the structure of the IMEI wherein the IMEI code is15-bit comprising: a type allocation code (TAC) which generallyrepresent UE models and indicates a manufacturer identifier; a SerialNumber (SNR) representing an individual serial number uniquelyidentifying each user equipment within the TAC and generally refers tothe manufacturing sequence number; and a Check Digit (CD)/Spare Digit(SD) which is not part of the digits transmitted when the IMEI ischecked. The Check Digit is intended to avoid manual transmissionerrors.

FIG. 5B illustrates the structure of the International Mobile stationEquipment Identity and Software Version Number (IMEISV) wherein theIMEISV code is 16-bit comprising: a type allocation code (TAC) whichgenerally represent UE models and indicates a manufacturer identifier; aSerial Number (SNR) representing an individual serial number uniquelyidentifying each user equipment within the TAC and generally refers tothe manufacturing sequence number; and a Software Version Number (SVN)which identifies the software version number of the user equipment.

Referring now to FIGS. 6A and 6B, FIGS. 6A and 6B are flowchartsillustrating a workflow of a RACS-capable network in accordance with anexample embodiment. At block 600, the RACS-capable network receives, forexample by using means such as the processor 12 and the communicationinterface 16, a registration request message comprising informationrelated to location registration to an access and mobility managementfunction (AMF) or a mobility management entity (MME) through a radioaccess network (RAN). In an example embodiment, the registration requestmessage indicates that the user equipment supports RACS.

Additionally or alternatively the RACS-capable network receives, forexample by using means such as the processor 12 and the communicationinterface 16, a registration request message, an attach request message,a tracking area update request message, or the like. These messagescomprising information related to location registration to the AMF orMME through the RAN.

After the RACS-capable network receives the registration request fromthe user equipment, the RACS-capable network, for example by using meanssuch as the processor 12, obtains an international mobile equipmentidentity (IMEI) or permanent equipment identifier (PEI) of the userequipment and extracting a type allocation code (TAC) from the IMEI orthe PEI as shown in block 610. In the IMEI or PEI the RACS-capablenetwork identifies the TAC of the UE.

The registration message, for a RACS capable UE (e.g. a UE indicatingRACS support) include, if available in the UE for the current radioconfiguration, a user equipment radio capability identification (ID)associated with the user equipment current radio configuration. The userequipment radio capability ID represents the user equipment's radioaccess capabilities information. As shown in block 612, the RACS-capablenetwork, for example by using means such as the processor 12, obtains auser equipment radio capability identification (ID) associated with theuser equipment. In an example embodiment, the AMF may receive the userequipment radio capability ID from the UE in the registration requestprocess.

The RACS-capable network then determines whether the user equipmentradio capability ID is a user equipment manufacturer ID or a public landmobile network (PLMN) assigned ID, for example by using means such asthe processor 12, at block 614.

The RACS-capable network then by using means such as the processor 12,compares the user equipment's TAC with a list of TACs enabled to operateaccording to a respective user equipment manufacturer ID at block 616.

As shown in block 618 in FIG. 6B, in circumstances where the userequipment's TAC appears on the list and the user equipment's userequipment radio capability ID is the public land mobile network (PLMN)assigned ID, the RACS-capable network, for example by using means suchas the processor 12, constructs a registration accept message, whereinthe registration accept message includes instructions for the userequipment to: 1) operate based on the user equipment manufacturer ID, 2)delete PLMN assigned IDs the user equipment stores for respective PLMNsand 3) trigger the user equipment to register with the user equipmentmanufacturer ID associated with a current user equipment radioconfiguration.

Additionally or alternatively, the RACS-capable network, for example byusing means such as the processor 12, constructs a registration acceptmessage, an attach accept message, a tracking area update acceptmessage, an user equipment configuration update command message, aglobally unique temporary ID (GUTI) reallocation command message, or thelike.

In circumstances where the user equipment's TAC does not appear on thelist and the user equipment's user equipment radio capability ID is theuser equipment manufacturer ID, the RACS-capable network, for example byusing means such as the processor 12, constructs the registration acceptmessage, wherein the registration accept message includes instructionsfor the user equipment to operate based on the PLMN assigned ID as shownin block 620.

In some embodiments, the RACS-capable network by using means such as theprocessor 12 may transmit the registration accept message to the userequipment as shown in block 622.

Additionally or alternatively, the RACS-capable network, for example byusing means such as the processor 12, transmits the registration acceptmessage, the attach accept message, the tracking area update acceptmessage, the user equipment configuration update command message, or theGUTI reallocation command message.

In some circumstances where the user equipment's TAC does not appear onthe list and the user equipment's user equipment radio capability ID isnot determined then the RACS-capable network, for example by using meanssuch as the processor 12, assigns the PLMN assigned ID and constructsthe registration accept message to include instructions for the userequipment to operate based on the PLMN assigned ID.

In circumstances where the user equipment's TAC appears on the list andthe user equipment's user equipment radio capability ID is notdetermined, the RACS-capable network, for example by using means such asthe processor 12, constructs the registration accept message, to includeinstructions for the user equipment to operate based on the userequipment manufacturer ID.

In some cases, the RACS-capable network, for example by using means suchas the processor 12, stores the assigned PLMN assigned ID as the userequipment radio capability ID along with their associated TACs on one ormore computer readable memories. The RACS-capable network furthertransmits, or example by using means such as the processor 12, anotification of a switch from the PLMN assigned ID to the user equipmentmanufacturer ID and vice-versa for a specific TAC.

When an indication is received to switch to the user equipmentmanufacturer ID for the specific TAC, the RACS-capable network, forexample by using means such as the processor 12, removes the specificTAC from the list of TACs enabled to operate according to the respectiveuser equipment manufacturer ID and removes the association of the PLMNassigned ID to the specific TAC.

In the case when the PLMN assigned ID becomes disassociated to any TAC,removing the dissociated PLMN assigned ID from storage, the RACS-capablenetwork, for example by using means such as the processor 12, transmitsa message instruction to a user equipment capabilities managementfunction (UCMF) to store the assigned PLMN assigned ID and associate theassigned PLMN assigned ID to the specific TAC.

Typically, the RACS-capable network determines, for example by usingmeans such as the processor 12, whether to commence assignment of theuser equipment manufacturer ID or the PLMN assigned ID by obtaining theTAC from the IMEI or the PEI, identifying a manufacturer identifier ofthe user equipment based on the TAC, and verifying the manufactureridentifier with a predetermined list of stored manufacturer identifiers.

FIG. 7 illustrates various components that may be utilized in a UE 700.The UE 700 includes a processor 702 that controls operation of the UE700. The processor 702 may be embodied in a number of different ways.For example, the processor may be embodied as one or more of varioushardware processing means such as a coprocessor, a microprocessor, acontroller, a digital signal processor (DSP), a processing element withor without an accompanying DSP, or various other circuitry includingintegrated circuits such as, for example, an ASIC (application specificintegrated circuit), an FPGA (field programmable gate array), amicrocontroller unit (MCU), a hardware accelerator, a special-purposecomputer chip, or the like. As such, in some embodiments, the processormay include one or more processing cores configured to performindependently. A multi-core processor may enable multiprocessing withina single physical package. Additionally or alternatively, the processormay include one or more processors configured in tandem via the bus toenable independent execution of instructions, pipelining and/ormultithreading.

In an example embodiment, the processor 702 may be configured to executeinstructions stored in memory device 704 or otherwise accessible to theprocessor. Alternatively or additionally, the processor may beconfigured to execute hard coded functionality. As such, whetherconfigured by hardware or software methods, or by a combination thereof,the processor may represent an entity (e.g., physically embodied incircuitry) capable of performing operations according to an embodimentof the present disclosure while configured accordingly. Thus, forexample, when the processor is embodied as an ASIC, FPGA or the like,the processor may be specifically configured hardware for conducting theoperations described herein. Alternatively, as another example, when theprocessor is embodied as an executor of instructions, the instructionsmay specifically configure the processor to perform the algorithmsand/or operations described herein when the instructions are executed.However, in some cases, the processor may be a processor of a specificdevice (e.g., an image processing system) configured to employ anembodiment of the present disclosure by further configuration of theprocessor by instructions for performing the algorithms and/oroperations described herein. The processor may include, among otherthings, a clock, an arithmetic logic unit (ALU) and logic gatesconfigured to support operation of the processor.

The processor 702 (and/or co-processors or any other circuitry assistingor otherwise associated with the processor) may be in communication withmemory 704 via a bus for passing information among components of the UE700. The memory 704 may be non-transitory and may include, for example,one or more volatile and/or non-volatile memories. In other words, forexample, the memory device may be an electronic storage device (e.g., acomputer readable storage medium) comprising gates configured to storedata (e.g., bits) that may be retrievable by a machine (e.g., acomputing device like the processor). The memory 704 may be configuredto store information, data, content, applications, instructions, or thelike for enabling the apparatus to carry out various functions inaccordance with an example embodiment of the present disclosure. Forexample, the memory 704 could be configured to buffer input data forprocessing by the processor. Additionally or alternatively, the memorydevice could be configured to store instructions for execution by theprocessor.

The communication interface 706 may be any means such as a device orcircuitry embodied in either hardware or a combination of hardware andsoftware that is configured to receive and/or transmit data from/to anetwork. In this regard, the communication interface may include, forexample, an antenna (or multiple antennas) and supporting hardwareand/or software for enabling communications with a wirelesscommunication network. Additionally or alternatively, the communicationinterface may include the circuitry for interacting with the antenna(s)to cause transmission of signals via the antenna(s) or to handle receiptof signals received via the antenna(s). In some environments, thecommunication interface may alternatively or also support wiredcommunication. As such, for example, the communication interface mayinclude a communication modem and/or other hardware/software forsupporting communication via cable, digital subscriber line (DSL),universal serial bus (USB) or other mechanisms.

The UE 700 may also include a housing that contains one or moretransmitters and one or more receivers to allow transmission andreception of data. The transmitter(s) and receiver(s) may be combinedinto one or more transceivers 708. One or more antennas 722 are attachedto the housing and electrically coupled to the transceiver 708. The UE700 may also include a digital signal processor (DSP) 710 for use inprocessing signals.

Referring now to FIG. 8, FIG. 8 is a flowchart illustrating a workflowof the UE 700 in accordance with an example embodiment. At block 800,the UE 700 transmits, for example by using means such as the processor702, a location registration request message to an access and mobilitymanagement function (AMF) or a mobility management entity (MME) througha radio access network (RAN).

Additionally or alternatively the UE 700 receives, for example by usingmeans such as the processor 702, a registration request message, anattach request message, a tracking area update request message, or thelike. These messages comprising information related to locationregistration to the AMF or MME through the RAN. As such, theregistration request message, attach request message, tracking areaupdate request message and similar terms may be used interchangeably torefer to messages comprising information related to locationregistration, transmitted, received and/or stored in accordance withembodiments of the present invention. Thus, use of any such messagesabove need to not be taken to limit the spirit and scope of embodimentsof the present invention.

In an example embodiment, the UE 700, for example by using means such asthe processor 702, indicates its support for RACS to AMF using UE MMCore Network Capability. For example, a UE that supports RACS and storesan applicable UE radio capability ID for the current UE RadioConfiguration in the PLMN shall signal the UE radio capability ID in theinitial registration procedure. If both a PLMN assigned ID for thecurrent PLMN and a UE manufacturer ID are both stored in the UE andapplicable in the PLMN, the UE shall signal the PLMN assigned UE radiocapability ID in the registration request message.

The UE 700 identifies, for example by using means such as the processor702, at block 810, a current user equipment radio configurationassociated with the registration request. In an example embodiment, theUE 700 may, for example by using means such as the processor 702, changeuser equipment radio configuration during a registration procedure inresponse to the UE 700 interacting with the UE Man-Machine-Interface(MMI) to turn off or turn on 5G or 4G, for example.

After the UE 700 transmits the location registration request, the UE 700receives, for example by using means such as the processor 702, aregistration accept message comprising a user equipment radio capabilityidentification (ID), at block 812. In an example embodiment, the UE 700receives the registration accept message from the RACS-capable network.

Additionally or alternatively, UE 700 receives, for example by usingmeans such as the processor 702, a registration accept message, anattach accept message, a tracking area update accept message, an userequipment configuration update command message, a globally uniquetemporary ID (GUTI) reallocation command message, or the like. As such,the registration accept message, attach accept message, tracking areaupdate accept message, user equipment configuration update commandmessage, GUTI reallocation command message and similar terms may be usedinterchangeably and transmitted, received and/or stored in accordancewith embodiments of the present invention. Thus, use of these messagesneed to not be taken to limit the spirit and scope of embodiments of thepresent invention.

In circumstances where the registration accept message indicatesinstructions to operate according to a user equipment manufacturer ID,the UE using means such as the processor 702 may delete stored publicland mobile network (PLMN) assigned IDs and re-register using the userequipment manufacturer ID associated with the current user equipmentradio configuration as the user equipment radio capability ID as shownin block 814. In an example embodiment, the UE 700 may, for example byusing means such as the processor 702, delete or erase all PLMN assignedIDs for the respective PLMN and thereafter will immediately registerusing the UE manufacturer ID. The UE 700 will, for example by usingmeans such as the processor 702, continue operating using the UEmanufacturer ID until the UE 700 receives an indication to operate witha PLMN assigned ID.

In circumstances where the registration accept message indicatesinstructions to operate according to a PLMN assigned ID, the UE 700associates, using means such as the processor 702, the PLMN assigned IDto the current user equipment radio configuration as shown in block 816.In an example embodiment, the UE 700 may, for example by using meanssuch as the processor 702, wait for the network to provide the UE radiocapability identification and upon receipt, the UE 700 is configured toassociate the UE radio capability identification with the current UEradio configuration. Additionally or alternatively, if the UE radiocapability ID was provided in the registration accept message, then theindication to operate with the PLMN assigned ID is implicit by theassignment of the PLMN assigned ID. Accordingly, the UE 700 will, forexample by using means such as the processor 702, continue to operateusing the PLMN assigned ID until the UE 700 receives an indication tooperate with the UE manufacturer ID.

As described above, FIGS. 6A, 6B, and 8 are flowcharts of an apparatus10, method, and computer program product according to an exampleembodiment of the disclosure. It will be understood that each block ofthe flowchart, and combinations of blocks in the flowcharts, may beimplemented by various means, such as hardware, firmware, processor,circuitry, and/or other devices associated with execution of softwareincluding one or more computer program instructions. For example, one ormore of the procedures described above may be embodied by computerprogram instructions. In this regard, the computer program instructionswhich embody the procedures described above may be stored by a memorydevice 14 of an apparatus employing an embodiment of the presentdisclosure and executed by a processor 12 of the apparatus. As will beappreciated, any such computer program instructions may be loaded onto acomputer or other programmable apparatus (e.g., hardware) to produce amachine, such that the resulting computer or other programmableapparatus implements the functions specified in the flowchart blocks.These computer program instructions may also be stored in acomputer-readable memory that may direct a computer or otherprogrammable apparatus to function in a particular manner, such that theinstructions stored in the computer-readable memory produce an articleof manufacture, the execution of which implements the function specifiedin the flowchart blocks. The computer program instructions may also beloaded onto a computer or other programmable apparatus to cause a seriesof operations to be performed on the computer or other programmableapparatus to produce a computer-implemented process such that theinstructions which execute on the computer or other programmableapparatus provide operations for implementing the functions specified inthe flowchart blocks.

A computer program product is therefore defined in those instances inwhich the computer program instructions, such as computer-readableprogram code portions, are stored by at least one non-transitorycomputer-readable storage medium with the computer program instructions,such as the computer-readable program code portions, being configured,upon execution, to perform the functions described above, such as inconjunction with the flowchart of FIG. 3. In other embodiments, thecomputer program instructions, such as the computer-readable programcode portions, need not be stored or otherwise embodied by anon-transitory computer-readable storage medium, but may, instead, beembodied by a transitory medium with the computer program instructions,such as the computer-readable program code portions, still beingconfigured, upon execution, to perform the functions described above.

Accordingly, blocks of the flowcharts support combinations of means forperforming the specified functions and combinations of operations forperforming the specified functions for performing the specifiedfunctions. It will also be understood that one or more blocks of theflowcharts, and combinations of blocks in the flowcharts, may beimplemented by special purpose hardware-based computer systems whichperform the specified functions, or combinations of special purposehardware and computer instructions.

In some embodiments, certain ones of the operations above may bemodified or further amplified. Furthermore, in some embodiments,additional optional operations may be included. Modifications,additions, or amplifications to the operations above may be performed inany order and in any combination.

Many modifications and other embodiments of the inventions set forthherein will come to mind to one skilled in the art to which theseinventions pertain having the benefit of the teachings presented in theforegoing descriptions and the associated drawings. Therefore, it is tobe understood that the inventions are not to be limited to the specificembodiments disclosed and that modifications and other embodiments areintended to be included within the scope of the appended claims.Although specific terms are employed herein, they are used in a genericand descriptive sense only and not for purposes of limitation.

What is claimed is:
 1. A method comprising: receiving, from a userequipment, a registration request message comprising information relatedto location registration to an access and mobility management function(AMF) or a mobility management entity (MME) through a radio accessnetwork (RAN); obtaining an international mobile equipment identity(IMEI) or permanent equipment identifier (PEI) of the user equipment andextracting a type allocation code (TAC) from the IMEI or the PEI;obtaining a user equipment radio capability identification (ID)associated with the user equipment; determining whether the userequipment radio capability ID is a user equipment manufacturer ID or apublic land mobile network (PLMN) assigned ID; comparing the userequipment's TAC with a list of TACs enabled to operate according to arespective user equipment manufacturer ID of a plurality of userequipment manufacturer IDs; in circumstances where the user equipment'sTAC appears on the list and the user equipment's user equipment radiocapability ID is the public land mobile network (PLMN) assigned ID:constructing a registration accept message, wherein the registrationaccept message includes instructions for the user equipment to: 1)operate based on the user equipment manufacturer ID, 2) delete PLMNassigned IDs the user equipment stores for respective PLMNs and 3)trigger the user equipment to register with the user equipmentmanufacturer ID associated with a current user equipment radioconfiguration; in circumstances where the user equipment's TAC does notappear on the list and the user equipment's user equipment radiocapability ID is the user equipment manufacturer ID: constructing theregistration accept message, wherein the registration accept messageincludes instructions for the user equipment to operate based on thePLMN assigned ID; and transmitting the registration accept message tothe user equipment.
 2. The method according to claim 1, furthercomprising: in circumstances where the user equipment's TAC does notappear on the list and the user equipment's user equipment radiocapability ID is not determined: assigning the PLMN assigned ID andconstructing the registration accept message, wherein the registrationaccept message includes instructions for the user equipment to operatebased on the PLMN assigned ID; and in circumstances where the userequipment's TAC appears on the list and the user equipment's userequipment radio capability ID is not determined: constructing theregistration accept message, wherein the registration accept messageincludes instructions for the user equipment to operate based on theuser equipment manufacturer ID.
 3. The method according to claim 1,further comprising: storing the assigned PLMN assigned ID as the userequipment radio capability ID along with their associated TACs;transmitting a notification of a switch from the PLMN assigned ID to theuser equipment manufacturer ID and vice-versa for a specific TAC; whenan indication is received to switch to the user equipment manufacturerID for the specific TAC, removing the specific TAC form the list of TACsenabled to operate according to the respective user equipmentmanufacturer ID and removing the association of the PLMN assigned ID tothe specific TAC; when the PLMN assigned ID becomes disassociated to anyTAC, removing the dissociated PLMN assigned ID from storage; andtransmitting a message instruction to a user equipment capabilitiesmanagement function (UCMF) to store the assigned PLMN assigned ID andassociate the assigned PLMN assigned ID to the specific TAC.
 4. Themethod according to claim 1, further comprising: determining whether tocommence assignment of the user equipment manufacturer ID or the PLMNassigned ID by: obtaining the TAC from the IMEI or the PEI; identifyinga manufacturer identifier of the user equipment based on the TAC; andverifying the manufacturer identifier with a predetermined list ofstored manufacturer identifiers.
 5. The method according to claim 1,wherein the user equipment radio capability ID represents the userequipment's radio access capabilities information.
 6. The methodaccording to claim 1, wherein the registration request message indicatesthat the user equipment supports user equipment radio capabilitysignaling (RACS).
 7. The method according to claim 1, furthercomprising: providing the instructions for the user equipment to operatebased on the PLMN assigned ID via a user equipment configuration updatemessage.
 8. The method according to claim 1, wherein a mapping betweenthe user equipment radio capability ID and its corresponding userequipment's radio access capabilities information is stored as adictionary entry in a network function or node.
 9. The method accordingto claim 8, wherein a user equipment capabilities management function(UCMF) stores the user equipment radio capability ID mappings in thePLMN and is configured to assign PLMN assigned IDs in the PLMN.
 10. Themethod according to claim 8, wherein the RAN caches the user equipmentradio capability ID mappings.
 11. The method according to claim 8,further comprising: querying the AMF for the mapping of the userequipment radio capability ID to the corresponding user equipment'sradio access capabilities information, wherein querying the AMF for themapping of the user equipment radio capability ID to the correspondinguser equipment's radio access capabilities information comprises the AMFproviding the user equipment radio capability ID to a user equipmentcapabilities management function (UCMF) to obtain the corresponding userequipment's radio access capabilities information.
 12. An apparatuscomprising at least one processor and at least one memory includingcomputer program code for one or more programs, the at least one memoryand the computer program code configured to, with the at least oneprocessor, cause the apparatus at least to: receive, from a userequipment, a registration request message comprising information relatedto location registration to an access and mobility management function(AMF) or a mobility management entity (MME) through a radio accessnetwork (RAN); obtain an international mobile equipment identity (IMEI)or permanent equipment identifier (PEI) of the user equipment andextract a type allocation code (TAC) from the IMEI or the PEI; obtain auser equipment radio capability identification (ID) associated with theuser equipment; determine whether the user equipment radio capability IDis a user equipment manufacturer ID or a public land mobile network(PLMN) assigned ID; compare the user equipment's TAC with a list of TACsenabled to operate according to a respective user equipment manufacturerID of a plurality of user equipment manufacturer IDs; in circumstanceswhere the user equipment's TAC appears on the list and the userequipment's user equipment radio capability ID is the public land mobilenetwork (PLMN) assigned ID: construct a registration accept message,wherein the registration accept message includes instructions for theuser equipment to: 1) operate based on the user equipment manufacturerID, 2) delete PLMN assigned IDs the user equipment stores for respectivePLMNs and 3) trigger the user equipment to register with the userequipment manufacturer ID associated with a current user equipment radioconfiguration; in circumstances where the user equipment's TAC does notappear on the list and the user equipment's user equipment radiocapability ID is the user equipment manufacturer ID: construct theregistration accept message, wherein the registration accept messageincludes instructions for the user equipment to operate based on thePLMN assigned ID; and transmit the registration accept message to theuser equipment.
 13. The apparatus according to claim 12, wherein the atleast one memory and the computer program code configured to, with theat least one processor, cause the apparatus at least to: incircumstances where the user equipment's TAC does not appear on the listand the user equipment's user equipment radio capability ID is notdetermined: assign the PLMN assigned ID and constructing theregistration accept message, wherein the registration accept messageincludes instructions for the user equipment to operate based on thePLMN assigned ID; and in circumstances where the user equipment's TACappears on the list and the user equipment's user equipment radiocapability ID is not determined: construct the registration acceptmessage, wherein the registration accept message includes instructionsfor the user equipment to operate based on the user equipmentmanufacturer ID.
 14. The apparatus according to claim 12, wherein the atleast one memory and the computer program code are configured to, withthe at least one processor, cause the apparatus at least to: store theassigned PLMN assigned ID as the user equipment radio capability IDalong with their associated TACs; transmit a notification of a switchfrom the PLMN assigned ID to the user equipment manufacturer ID andvice-versa for a specific TAC; when an indication is received to switchto the user equipment manufacturer ID for the specific TAC, remove thespecific TAC form the list of TACs enabled to operate according to therespective user equipment manufacturer ID and remove the association ofthe PLMN assigned ID to the specific TAC; when the PLMN assigned IDbecomes disassociated to any TAC, remove the dissociated PLMN assignedID from storage; and transmit a message instruction to a user equipmentcapabilities management function (UCMF) to store the assigned PLMNassigned ID and associate the assigned PLMN assigned ID to the specificTAC.
 15. The apparatus according to claim 12, wherein the at least onememory and the computer program code configured to, with the at leastone processor, cause the apparatus at least to: determine whether tocommence assignment of the user equipment manufacturer ID or the PLMNassigned ID by: obtain the TAC from the IMEI or the PEI; identify amanufacturer identifier of the user equipment based on the TAC; andverify the manufacturer identifier with a predetermined list of storedmanufacturer identifiers.
 16. The apparatus according to claim 12,wherein the user equipment radio capability ID represents the userequipment's radio access capabilities information.
 17. The apparatusaccording to claim 12, wherein the registration request messageindicates that the user equipment supports user equipment radiocapability signaling (RACS).
 18. An apparatus comprising at least oneprocessor and at least one memory including computer program code forone or more programs, the at least one memory and the computer programcode configured to, with the at least one processor, cause the apparatusat least to: transmit a location registration request message to anaccess and mobility management function (AMF) or a mobility managemententity (MME) through a radio access network (RAN); identify a currentuser equipment radio configuration associated with the locationregistration request message; receive a registration accept messagecomprising a user equipment radio capability identification (ID); incircumstances where the registration accept message indicatesinstructions to operate according to a user equipment manufacturer ID:delete stored public land mobile network (PLMN) assigned IDs andre-register using the user equipment manufacturer ID associated with thecurrent user equipment radio configuration as the user equipment radiocapability ID; and in circumstances where the registration acceptmessage indicates instructions to operate according to a PLMN assignedID: associate the PLMN assigned ID to the current user equipment radioconfiguration.
 19. The apparatus according to claim 18, wherein the userequipment radio capability ID represents a user equipment's radio accesscapabilities information.
 20. The apparatus according to claim 18,wherein the at least one memory and the computer program code areconfigured to, with the at least one processor, cause the apparatus atleast to: signal the PLMN assigned ID in the location registrationrequest message when both of the PLMN assigned ID for the current PLMNand the user equipment manufacturer ID are stored in the user equipmentand applicable in the PLMN.